Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
686-tree-1
name
1051
tree-preservation-order

undefined

686-tpo-1
uprn
address-text
point
POINT (-1.018108 50.881750)
geometry
MULTIPOLYGON (((-1.018066 50.881745,-1.018068 50.881754,-1.018073 50.881761,-1.018083 50.881767,-1.018095 50.881771,-1.018108 50.881773,-1.018121 50.881772,-1.018133 50.881768,-1.018142 50.881762,-1.018149 50.881755,-1.018151 50.881746,-1.018149 50.881738,-1.018143 50.881730,-1.018134 50.881724,-1.018122 50.881720,-1.018109 50.881719,-1.018096 50.881720,-1.018084 50.881724,-1.018074 50.881730,-1.018068 50.881737,-1.018066 50.881745)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL